|
||||
| InfoRMS | ||||
| Displaying 14 issues at 16/Jul/25 11:22 AM. |
| Key | Summary | Description | Resolution | Resolution Description |
|---|---|---|---|---|
| PS-210 | DiagnosticReport.Status Not Fixed in CA Core, Fixed =Final in PS-CA |
Summary: DiagnosticReport.Status Not Fixed in CA Core, Fixed =Final in PS-CA
Existing Wording: Proposed Wording: Comment: DiagnosticReport.Status Not Fixed in CA Core, Fixed =Final in PS-CA IPS CI build changed to not fixed; previously fixed = "final"; PS-CA should change back to not fixed. Submitted by: Kenn Sinn Infoway |
Persuasive | Agreed, the fixed constraint will be removed |
| PS-199 | Suggest to remove |
Summary: Suggest to remove
Existing Wording: Comments See additionalBinding extension. IPS-UV no longer flags this as a Must Support element. It is not currently flagged as Must Support in PS-CA, as stakeholders have indicated the element may not be supported by the majority of systems today. Systems that do support the element are encouraged to include it in generated Patient Summary documents, and support it when received. Proposed Wording: Comments See additionalBinding extension. Comment: Suggest to remove Submitted by: Linda Parisien Canada Health Infoway |
Persuasive | This is the comment for route - remove the two indicated paragraphs:
IPS-UV no longer flags this as a Must Support element. It is not currently flagged as Must Support in PS-CA, as stakeholders have indicated the element may not be supported by the majority of systems today. Systems that do support the element are encouraged to include it in generated Patient Summary documents, and support it when received. |
| PS-196 | Changed for the current valueset definition |
Summary: Changed for the current valueset definition
Existing Wording: Binding The site at which the vaccine was administered. Proposed Wording: Binding The anatomical site where the immunizing agent was administered. CodesForImmunizationSiteOfAdministration (example)ImmunizationAdministeredAnatomicalSiteCode Comment: Changed for the current valueset definition Submitted by: Myriam Talantikit Canada Health Infoway |
Persuasive | Agreed. Update definition |
| PS-195 | Not relevant anymore, suggest to remove |
Summary: Not relevant anymore, suggest to remove
Existing Wording: Comments The development of a FHIR ValueSet & Terminology Gateway subset for this element is underway. Given that the migration of terminology from the CVC to NVC is underway, and that this element is no longer MS in PS-CA or IPS, the profiling on this binding has been temporarily removed and will be reapplied in future updates once there is an established subset to point to. Proposed Wording: delete Comment: Not relevant anymore, suggest to remove Submitted by: Myriam Talantikit Canada Health Infoway |
Persuasive | Agreed, the text will be removed |
| PS-192 | Add valueset current definition |
Summary: Add valueset current definition
Existing Wording: PassiveHistoricalImmunizingAgentCode (preferred) Equivalently recommended for use when conveying when passive immunization products are used. Proposed Wording: PassiveHistoricalImmunizingAgentCode (preferred) This refset is intended to capture the immunization history and includes concepts represented by a generic description for a passive immunizing agent that was previously administered to the client Comment: Add valueset current definition and remove the old paragraph Submitted by: Myriam Talantikit Canada Health Infoway |
Persuasive | Agreed, text description will be updated as proposed
PassiveHistoricalImmunizingAgentCode (preferred) _This refset is intended to capture the immunization history and includes concepts represented by a generic description for a passive immunizing agent that was previously administered to the client_ |
| PS-191 | Add valueset current definition |
Summary: Add valueset current definition
Existing Wording: PassiveAdministeredImmunizingAgentCode (preferred) Equivalently recommended for use when conveying when passive immunization products are used. Proposed Wording: PassiveAdministeredImmunizingAgentCode (preferred) This refset is intended to capture the product administered at the point of immunization and includes the passive immunizing agent tradenames that are currently licensed for use in Canada, those obtained through special access programs for use in Canada, and those that were never licensed in Canada. Comment: Add valueset current definition and remove the old paragraph Submitted by: Myriam Talantikit Canada Health Infoway |
Persuasive | Agreed, text description will be updated as proposed
PassiveAdministeredImmunizingAgentCode (preferred) _This refset is intended to capture the product administered at the point of immunization and includes the passive immunizing agent tradenames that are currently licensed for use in Canada, those obtained through special access programs for use in Canada, and those that were never licensed in Canada._ |
| PS-190 | Add valueset current definition |
Summary: Add valueset current definition
Existing Wording: VaccineHistoricalNameCode (preferred) Equivalently recommended for use when conveying vaccine generic names for scenarios when brand names…. Proposed Wording: VaccineHistoricalNameCode (preferred) This refset is intended to capture the immunization history and includes concepts represented by a generic description for a vaccine that was previously administered to the client Comment: Add valueset current definition and remove the old paragraph Submitted by: Myriam Talantikit Canada Health Infoway |
Persuasive | Agreed, text description will be updated as proposed
VaccineHistoricalNameCode (preferred) _This refset is intended to capture the immunization history and includes concepts represented by a generic description for a vaccine that was previously administered to the client_ |
| PS-189 | Suggest removing these additional bindings as mentioned below |
Summary: Suggest removing these additional bindings as mentioned below
Existing Wording: Comments See additionalBinding extension. Future releases of PS-CA may require use of coded entries. In this release, however, implementations that support codings are encouraged to send the codings for codeable concepts if they are available. Consistent with FHIR best practice, receivers should not produce failures or rejections if codings are received. Vendors should expect that some jurisdictions may further constrain support of this element within the context of their own jurisdictional content. IPS-UV Note: Several kinds of vaccine product coding could be provided. The IPS assumes that either the type of the vaccine for particular disease or diseases (e.g. MMR vaccine) against which the patient has been immunized is provided; or the known absent/unknown. Other coded information can be provided as well as: 1. The IDMP Pharmaceutical Product Identifier (PhPID), Level 1, [Substance(s)]. Example: Amoxicillin and Clavulanate Potassium; or any other equivalent coded concept. 2. The IDMP Pharmaceutical Product Identifier (PhPID), Level 2 [Substance(s) + Strength + reference strength]. Example: Amoxicillin 875 mg and Clavulanate Potassium 125 mg; or any other equivalent coded concept. 3. The IDMP Pharmaceutical Product Identifier (PhPID), Level 3 [Substance(s) + administrable dose form]. Example: Amoxicillin and Clavulanate Potassium, Oral Tablet; or any other equivalent coded concept. 4. The IDMP Pharmaceutical Product Identifier (PhPID), Level 4 [Substance(s) + strength + reference strength + administrable dose form]. Example: Amoxicillin 875 mg and clavulanate potassium 125 mg, oral tablet; or any other equivalent coded concept. 5. The IDMP Medicinal Product Identifier (MPID) or any equivalent Medicinal Product Identifier. IDMP MPID uniquely identifies a Medicinal Product, reflecting (but not replacing) any other authorization numbers allocated by a regulator. MPID implies one (set of) PhPID. The MPID shall use a common segment pattern related to a Medicinal Product, which, when each segment is valued shall define a specific MPID concept. 6. The IDMP Packaged Medicinal Product Identifier (PCID) or any equivalent Packaged Medicinal Product Identifier. Uniquely identifies a Medicinal Product based on its packaging. This implies one MPID can be associated with more than one PCID, if the same Medicinal Product has more than one type of package. 7. Any other kind of code that that identifies, classifies or clusters the administered product (e.g. the medicinal product or the product class). The value sets used for the PhPID, MPID and PCID identifiers are provisional and include only few equivalent concepts used for exemplification purposes, they will be updated with real IDMP identifiers when they will become available. Proposed Wording: delete Comment: Suggest removing these additional bindings as mentioned below Submitted by: Myriam Talantikit Canada Health Infoway |
Not Persuasive | The set of bindings should remain. The removal of the IDMP text is covered by ticket PS-152 |
| PS-188 | Suggest to remove this text as in CA we are not using the IPS-UV vaccine concepts, because that would be a partial set of codes. No Canadian Trade names or Brand names would be available from that set of codes |
Summary: Suggest to remove this text as in CA we are not using the IPS-UV vaccine concepts, because that would be a partial set of codes. No Canadian Trade names or Brand names would be available from that set of codes
Existing Wording: IPS-UV Note: Several kinds of vaccine product coding could be provided. The IPS assumes that either the type of the vaccine for particular disease or diseases (e.g. MMR vaccine) against which the patient has been immunised is provided; or the known absent/unknown code. Other coded information can be provided as well as: the Pharmaceutical and medicinal product identifiers, when available, or equivalent coded concepts; the WHO ATC codes; or any other kind of code that that identifies, classifies or cluster the administered product. Proposed Wording: delete Comment: Suggest to remove this text as in CA we are not using the IPS-UV vaccine concepts, because that would be a partial set of codes. No Canadian Trade names or Brand names would be available from that set of codes. I would add here the note on the 4 Infoway valuesets that should be used in CA: Note: VaccineHistoricalNameCode, PassiveAdministeredImmunizingAgentCode, and PassiveHistoricalImmunizingAgentCode equivalently preferred to the primary binding as they convey codes that are intended to be utilized in different contexts (e.g., passive agents) Submitted by: Linda Parisien Canada Health Infoway |
Not Persuasive with Modification | Keep the IPS text and add:
_The IPS-UV vaccine concepts are not used in Canadian implementations as they do not include Canadian trade or brand names. Implementers should use the following pan-Canadian value sets, depending on context: "VaccineHistoricalNameCode", "PassiveAdministeredImmunizingAgentCode", and "PassiveHistoricalImmunizingAgentCode", which are equivalently preferred alongside the primary binding._ |
| PS-186 | Infoway valuesets for different scope for Route of administration. |
Summary: Infoway valuesets for different scope for Route of administration.
Existing Wording: EDQM route of administration MedicineRouteOfAdministrationUvIps, HL7 v3 route of administration v3.RouteOfAdministration Proposed Wording: delete Comment: Infoway has developed multiple valuesets for different scope for Route of administration. The only binding should be the preferred one above. EDQM is not in use in Canada per say, SNOMED CT CA is aligned with EDQM. Submitted by: Linda Parisien Canada Health Infoway |
Not Persuasive with Modification | Keep the additional bindings, but add a note:
" While this additional binding is not primarily used in the Canadian healthcare context, it is retained to support potential use of PS-CA internationally and IPS within Canada. Implementers should be aware that this binding may not comprehensively represent all Canadian route of administration codes" |
| PS-185 | Suggestion to delete all this paragraph as it is not relevant anymore |
Summary: Suggestion to delete all this paragraph as it is not relevant anymore
Existing Wording: The development of a FHIR ValueSet & Terminology Gateway subset for this element is underway. Given that the migration of terminology from the CVC to NVC is underway, and that this element is no longer MS in PS-CA or IPS, the profiling on this binding has been temporarily removed and will be re-applied in future updates once there is an established subset to point to. Proposed Wording: delete Comment: Suggestion to delete all this paragraph as it is not relevant anymore Submitted by: Myriam Talantikit Canada Health Infoway |
Persuasive | Agreed, the identified text will be removed from the site element. |
| PS-184 | Addition: current existing valueset for anatomical site codes |
Summary: Addition: current existing valueset for anatomical site codes
Existing Wording: Proposed Wording: Added preferred binding of ImmunizationAdministrationAnatomicalSiteCode Comment: Addition: current existing valueset for anatomical site codes Submitted by: Myriam Talantikit Canada Health Infoway |
Persuasive with Modification | Add ImmunizationAdministrationAnatomicalSiteCode as preferred binding |
| PS-183 | In Canada, we have developed vaccine concepts that would not be available from any of the IPS Vaccine Code, not the WHO ATC |
Summary: In Canada, we have developed vaccine concepts that would not be available from any of the IPS Vaccine Code, not the WHO ATC
Existing Wording: IPS Vaccine Code VaccinesUvIps - WHO ATC WhoAtcUvIps Proposed Wording: delete Comment: In Canada, we have developed vaccine concepts that would not be available from any of the IPS Vaccine Code, not the WHO ATC. Providing these bindings, means that only partial information on vaccine could be captured.If we decide to still keep these above bindings in the PS-CA, a Note to that effect should be provided. Submitted by: Linda Parisien Canada Health Infoway |
Not Persuasive with Modification | Keep the bindings and add a note highlighting that the WHO ATC WhoAtcUvIps does not provide coverage for all vaccines used in Canada. |
| PS-152 | There’s significant text around the use of IDMP levels, which aren’t used in Canada. |
Summary: There’s significant text around the use of IDMP levels, which aren’t used in Canada.
Existing Wording: Proposed Wording: Comment: There’s significant text around the use of IDMP levels, which aren’t used in Canada. SNOMED is currently mapping to IDMP as well. Suggest all the content around IDMP be removed if it is not applicable, as it may confuse or overwhelm readers/implementers. They were included in PS-CA because the IPS mentions them all (https://build.fhir.org/ig/HL7/fhir-ips/StructureDefinition-Immunization-uv-ips-definitions.html#key_Immunization.vaccineCode) – but IPS has no included any bindings to them to date. Submitted by: Linda Parisien Myriam Talantikit Infoway |
Persuasive | Remove the IPS UV note text in its entirety |
| Generated at Wed Jul 16 11:22:16 EDT 2025 by Sonia Balgah using Jira 10.3.2#10030002-sha1:0a5d322ae1b7fd5b314be5b31a27d9661f8301b2. |